You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by Dilpreet Singh <di...@gmail.com> on 2018/01/21 09:54:02 UTC
Re: [Mifos-developer] Assistance with Server Side Testing in Apache
Fineract for In-App notifications
Hello all,
These are some questions along with their answers which can be helpful:
*Q. How to test this feature?*
*A.* Currently an event triggered notification is enabled which should send
a notification to the android app when a loan is successfully approved.
So, after making a client -> then a self service user, one should apply for
a loan either from here https://mobile.openmf.org/#/clients for their
respective client created or can apply from loan from the app itself. Then
approve that loan from the platform i.e. https://mobile.openmf.org/#/.
Approving the loan should send a notification to the user android app but
notifications don't get delivered as explained by Ed.
*Q. How to find the problem cause?*
*A.* You can approve a loan for this client:
https://mobile.openmf.org/#/viewclient/1 and log the values for this *res *
variable: https://github.com/apache/fineract/pull/421/files#diff-ddac4ffff7
6fe35a196366c822441ec2R114 which will help to know the cause.
Dilpreet
On 19 January 2018 at 23:50, Ed Cable <ed...@mifos.org> wrote:
> Hello all,
>
> The team working on the mobile banking app that consumes the Apache
> Fineract self-service APIs as well as the notifications APIs for
> event-based as well as schedule campaign notifications has been testing out
> in-app notifications and narrowed down the most recent issues to being on
> the side of the server.
>
> Dilpreet is successfully able to have a notification delivered to the
> mobile banking app when using a service like pushtry by including the
> requisite server ID and the GCM token for the phone.
>
> However when attempting to have these in-app notifications be generated by
> either a scheduled campaign in Fineract or an event triggered by Fineract,
> the notifications don't get delivered to the mobile device.
>
> Here's the line of code where Dilpreet has narrowed the issue down to: (
> logging *res *variable: https://github.com/apache/fineract/
> pull/421/files#diff-ddac4ffff76fe35a196366c822441ec2R114 will be *very
> helpful* in finding the problem cause.
>
>
> If you'd like to test out the latest APK, it can be downloaded at:
> https://drive.google.com/open?id=0ByeK44WJrHIvcUpEZDdZVnhRUXdWM
> jZYX0U2cXc4ZXZyc0Fv
>
> You will first to need to create a client account on the mobile testing
> instance at https://mobile.openmf.org (mifos/password) and then you can
> use the app to register and create a self-service user authenticated
> against that client account.
>
> The GCM token for each mobile device gets registered on the server
> automatically once a self-service user logs in and goes to the home screen
> in the app.
>
> The in-app notifications are generated using the similar event-based and
> campaigns that were leveraged for SMS after they were extended by Nazeer.
>
> Dilpreet, could you share more details and any clarifying questions?
>
> Ed
>
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edcable@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>
>
>
> ------------------------------------------------------------
> ------------------
> 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-developer@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>
Re: [Mifos-developer] Assistance with Server Side Testing in Apache
Fineract for In-App notifications
Posted by Ed Cable <ed...@mifos.org>.
Piyadassi,
The demo and demo3 tenants have the latest stable release on it. The mobile
tenant is our staging server and has the code that's being worked on for
next release on it.
You should be able to create a self-service user via the actual mobile
banking app for your client. But first you must ensure that on
mobile.openmf.org there is a client with your phone and email credentials.
You can then create the self-service user for that client when you open the
mobile banking app for the first time.
Ed
On Fri, Feb 16, 2018 at 1:49 AM, Piyadassi Shakya <shakyapiyadassi@gmail.com
> wrote:
> Hi Steve,
>
> * I tried to test this on mobile.openmf.org but couldn't create
> selfservice
> user for the client. How do we do that?
>
> * What is different in demo.openmf.org, demo3.openmf.org and
> mobile.openmf.org
> * and I just found out that notification service is available in
> mobile.openmf.org but not in demo. ....
>
>
>
> With Regards
> Piyadassi
>
> On Fri, Feb 16, 2018 at 8:51 AM, Steve Conrad <sc...@gmail.com> wrote:
>
> > I created a fix for this issue so that an SMS campaign handles triggered
> > messages the same way that scheduled messages are handled. If the message
> > is a notification, it goes to the GCM service. Otherwise, it goes to the
> > standard SMS service.
> >
> > I submitted a PR for this issue: https://github.com/apache/
> > fineract/pull/442
> >
> > Thanks,
> > Steve
> >
> >
> > On Sun, Jan 21, 2018 at 3:54 AM, Dilpreet Singh <di...@gmail.com>
> > wrote:
> >
> > > Hello all,
> > >
> > > These are some questions along with their answers which can be helpful:
> > >
> > > *Q. How to test this feature?*
> > > *A.* Currently an event triggered notification is enabled which should
> > > send a notification to the android app when a loan is successfully
> > approved.
> > > So, after making a client -> then a self service user, one should apply
> > > for a loan either from here https://mobile.openmf.org/#/clients for
> > their
> > > respective client created or can apply from loan from the app itself.
> > Then
> > > approve that loan from the platform i.e. https://mobile.openmf.org/#/.
> > >
> > > Approving the loan should send a notification to the user android app
> but
> > > notifications don't get delivered as explained by Ed.
> > >
> > > *Q. How to find the problem cause?*
> > > *A.* You can approve a loan for this client:
> > https://mobile.openmf.org/#/
> > > viewclient/1 and log the values for this *res *variable: https:/
> > > /github.com/apache/fineract/pull/421/files#diff-ddac4ffff76f
> > > e35a196366c822441ec2R114 which will help to know the cause.
> > >
> > >
> > > Dilpreet
> > >
> > > On 19 January 2018 at 23:50, Ed Cable <ed...@mifos.org> wrote:
> > >
> > >> Hello all,
> > >>
> > >> The team working on the mobile banking app that consumes the Apache
> > >> Fineract self-service APIs as well as the notifications APIs for
> > >> event-based as well as schedule campaign notifications has been
> testing
> > out
> > >> in-app notifications and narrowed down the most recent issues to being
> > on
> > >> the side of the server.
> > >>
> > >> Dilpreet is successfully able to have a notification delivered to the
> > >> mobile banking app when using a service like pushtry by including the
> > >> requisite server ID and the GCM token for the phone.
> > >>
> > >> However when attempting to have these in-app notifications be
> generated
> > >> by either a scheduled campaign in Fineract or an event triggered by
> > >> Fineract, the notifications don't get delivered to the mobile device.
> > >>
> > >> Here's the line of code where Dilpreet has narrowed the issue down
> to: (
> > >> logging *res *variable: https://github.com/apache/fineract/pu
> > >> ll/421/files#diff-ddac4ffff76fe35a196366c822441ec2R114 will be *very
> > >> helpful* in finding the problem cause.
> > >>
> > >>
> > >> If you'd like to test out the latest APK, it can be downloaded at:
> > >> https://drive.google.com/open?id=0ByeK44WJrHIvcUpEZDdZVn
> > >> hRUXdWMjZYX0U2cXc4ZXZyc0Fv
> > >>
> > >> You will first to need to create a client account on the mobile
> testing
> > >> instance at https://mobile.openmf.org (mifos/password) and then you
> can
> > >> use the app to register and create a self-service user authenticated
> > >> against that client account.
> > >>
> > >> The GCM token for each mobile device gets registered on the server
> > >> automatically once a self-service user logs in and goes to the home
> > screen
> > >> in the app.
> > >>
> > >> The in-app notifications are generated using the similar event-based
> and
> > >> campaigns that were leveraged for SMS after they were extended by
> > Nazeer.
> > >>
> > >> Dilpreet, could you share more details and any clarifying questions?
> > >>
> > >> Ed
> > >>
> > >>
> > >>
> > >> --
> > >> *Ed Cable*
> > >> President/CEO, Mifos Initiative
> > >> edcable@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>
> > >>
> > >>
> > >> ------------------------------------------------------------
> > >> ------------------
> > >> 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-developer@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-developer@lists.sourceforge.net
> > > Unsubscribe or change settings at:
> > > https://lists.sourceforge.net/lists/listinfo/mifos-developer
> > >
> >
>
--
*Ed Cable*
President/CEO, Mifos Initiative
edcable@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] Assistance with Server Side Testing in Apache
Fineract for In-App notifications
Posted by Piyadassi Shakya <sh...@gmail.com>.
Hi Steve,
* I tried to test this on mobile.openmf.org but couldn't create selfservice
user for the client. How do we do that?
* What is different in demo.openmf.org, demo3.openmf.org and
mobile.openmf.org
* and I just found out that notification service is available in
mobile.openmf.org but not in demo. ....
With Regards
Piyadassi
On Fri, Feb 16, 2018 at 8:51 AM, Steve Conrad <sc...@gmail.com> wrote:
> I created a fix for this issue so that an SMS campaign handles triggered
> messages the same way that scheduled messages are handled. If the message
> is a notification, it goes to the GCM service. Otherwise, it goes to the
> standard SMS service.
>
> I submitted a PR for this issue: https://github.com/apache/
> fineract/pull/442
>
> Thanks,
> Steve
>
>
> On Sun, Jan 21, 2018 at 3:54 AM, Dilpreet Singh <di...@gmail.com>
> wrote:
>
> > Hello all,
> >
> > These are some questions along with their answers which can be helpful:
> >
> > *Q. How to test this feature?*
> > *A.* Currently an event triggered notification is enabled which should
> > send a notification to the android app when a loan is successfully
> approved.
> > So, after making a client -> then a self service user, one should apply
> > for a loan either from here https://mobile.openmf.org/#/clients for
> their
> > respective client created or can apply from loan from the app itself.
> Then
> > approve that loan from the platform i.e. https://mobile.openmf.org/#/.
> >
> > Approving the loan should send a notification to the user android app but
> > notifications don't get delivered as explained by Ed.
> >
> > *Q. How to find the problem cause?*
> > *A.* You can approve a loan for this client:
> https://mobile.openmf.org/#/
> > viewclient/1 and log the values for this *res *variable: https:/
> > /github.com/apache/fineract/pull/421/files#diff-ddac4ffff76f
> > e35a196366c822441ec2R114 which will help to know the cause.
> >
> >
> > Dilpreet
> >
> > On 19 January 2018 at 23:50, Ed Cable <ed...@mifos.org> wrote:
> >
> >> Hello all,
> >>
> >> The team working on the mobile banking app that consumes the Apache
> >> Fineract self-service APIs as well as the notifications APIs for
> >> event-based as well as schedule campaign notifications has been testing
> out
> >> in-app notifications and narrowed down the most recent issues to being
> on
> >> the side of the server.
> >>
> >> Dilpreet is successfully able to have a notification delivered to the
> >> mobile banking app when using a service like pushtry by including the
> >> requisite server ID and the GCM token for the phone.
> >>
> >> However when attempting to have these in-app notifications be generated
> >> by either a scheduled campaign in Fineract or an event triggered by
> >> Fineract, the notifications don't get delivered to the mobile device.
> >>
> >> Here's the line of code where Dilpreet has narrowed the issue down to: (
> >> logging *res *variable: https://github.com/apache/fineract/pu
> >> ll/421/files#diff-ddac4ffff76fe35a196366c822441ec2R114 will be *very
> >> helpful* in finding the problem cause.
> >>
> >>
> >> If you'd like to test out the latest APK, it can be downloaded at:
> >> https://drive.google.com/open?id=0ByeK44WJrHIvcUpEZDdZVn
> >> hRUXdWMjZYX0U2cXc4ZXZyc0Fv
> >>
> >> You will first to need to create a client account on the mobile testing
> >> instance at https://mobile.openmf.org (mifos/password) and then you can
> >> use the app to register and create a self-service user authenticated
> >> against that client account.
> >>
> >> The GCM token for each mobile device gets registered on the server
> >> automatically once a self-service user logs in and goes to the home
> screen
> >> in the app.
> >>
> >> The in-app notifications are generated using the similar event-based and
> >> campaigns that were leveraged for SMS after they were extended by
> Nazeer.
> >>
> >> Dilpreet, could you share more details and any clarifying questions?
> >>
> >> Ed
> >>
> >>
> >>
> >> --
> >> *Ed Cable*
> >> President/CEO, Mifos Initiative
> >> edcable@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>
> >>
> >>
> >> ------------------------------------------------------------
> >> ------------------
> >> 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-developer@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-developer@lists.sourceforge.net
> > Unsubscribe or change settings at:
> > https://lists.sourceforge.net/lists/listinfo/mifos-developer
> >
>
Re: [Mifos-developer] Assistance with Server Side Testing in Apache
Fineract for In-App notifications
Posted by Steve Conrad <sc...@gmail.com>.
I created a fix for this issue so that an SMS campaign handles triggered
messages the same way that scheduled messages are handled. If the message
is a notification, it goes to the GCM service. Otherwise, it goes to the
standard SMS service.
I submitted a PR for this issue: https://github.com/apache/fineract/pull/442
Thanks,
Steve
On Sun, Jan 21, 2018 at 3:54 AM, Dilpreet Singh <di...@gmail.com>
wrote:
> Hello all,
>
> These are some questions along with their answers which can be helpful:
>
> *Q. How to test this feature?*
> *A.* Currently an event triggered notification is enabled which should
> send a notification to the android app when a loan is successfully approved.
> So, after making a client -> then a self service user, one should apply
> for a loan either from here https://mobile.openmf.org/#/clients for their
> respective client created or can apply from loan from the app itself. Then
> approve that loan from the platform i.e. https://mobile.openmf.org/#/.
>
> Approving the loan should send a notification to the user android app but
> notifications don't get delivered as explained by Ed.
>
> *Q. How to find the problem cause?*
> *A.* You can approve a loan for this client: https://mobile.openmf.org/#/
> viewclient/1 and log the values for this *res *variable: https:/
> /github.com/apache/fineract/pull/421/files#diff-ddac4ffff76f
> e35a196366c822441ec2R114 which will help to know the cause.
>
>
> Dilpreet
>
> On 19 January 2018 at 23:50, Ed Cable <ed...@mifos.org> wrote:
>
>> Hello all,
>>
>> The team working on the mobile banking app that consumes the Apache
>> Fineract self-service APIs as well as the notifications APIs for
>> event-based as well as schedule campaign notifications has been testing out
>> in-app notifications and narrowed down the most recent issues to being on
>> the side of the server.
>>
>> Dilpreet is successfully able to have a notification delivered to the
>> mobile banking app when using a service like pushtry by including the
>> requisite server ID and the GCM token for the phone.
>>
>> However when attempting to have these in-app notifications be generated
>> by either a scheduled campaign in Fineract or an event triggered by
>> Fineract, the notifications don't get delivered to the mobile device.
>>
>> Here's the line of code where Dilpreet has narrowed the issue down to: (
>> logging *res *variable: https://github.com/apache/fineract/pu
>> ll/421/files#diff-ddac4ffff76fe35a196366c822441ec2R114 will be *very
>> helpful* in finding the problem cause.
>>
>>
>> If you'd like to test out the latest APK, it can be downloaded at:
>> https://drive.google.com/open?id=0ByeK44WJrHIvcUpEZDdZVn
>> hRUXdWMjZYX0U2cXc4ZXZyc0Fv
>>
>> You will first to need to create a client account on the mobile testing
>> instance at https://mobile.openmf.org (mifos/password) and then you can
>> use the app to register and create a self-service user authenticated
>> against that client account.
>>
>> The GCM token for each mobile device gets registered on the server
>> automatically once a self-service user logs in and goes to the home screen
>> in the app.
>>
>> The in-app notifications are generated using the similar event-based and
>> campaigns that were leveraged for SMS after they were extended by Nazeer.
>>
>> Dilpreet, could you share more details and any clarifying questions?
>>
>> Ed
>>
>>
>>
>> --
>> *Ed Cable*
>> President/CEO, Mifos Initiative
>> edcable@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>
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> 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-developer@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-developer@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>