Hello Arnold,
For the classical UI some events were not passed to the UI (details
URL) because the Event property names were not matching.
I think it is still open ..
https://github.com/openMF/community-app/pull/3441
Regards
Victor
El mié, 18 may 2022 a las 10:10, Arnold Galovics ()
escribió:
I'm cc'ing @Pranjal Goswami who originally
designed the notifications framework.
Here's one of the original design docs on the notification storage and
topic subscription.
https://docs.google.com/presentation/d/1jzqEQxxRYa1ZvN_SXLRwDgXBux1cb3_IMBWbdS7rRV0/edit?usp=sharing
Once it's fully imple
Hi guys,
Thanks for the feedback. I can only agree with you, we don't want to lose
features that are potentially used.
I was probably not crystal clear when I mentioned the term "notification
topic". I was mainly referring to the "topic" and "topic_subscriber" tables
which are currently not expos
Yes, we have to be careful about removing things, that is probably an
unspoken principle on this project as we don't know how it's being used.
(unfortunately)
However, if it makes sense from an architectural perspective to rationalize
the notification and event handling frameworks, then I would sug
Hi Arnold,
I have some organizations using the notification feature effectively for
sanctioning or disbursing the loan accounts based on the notifications
which they receive. It is mainly useful when there are different levels of
approvals for the loan cycle.
(user configuration document for this
Hi Anold,
I restarted the instance and requests are getting replies now on the remote
instance.
I am still getting the SQLExceptions
Thanks again for your help.
On Wed, May 18, 2022 at 12:48 PM Kigred Developer <
kigred.develo...@gmail.com> wrote:
> Hi Anold,
>
> FYI this is what I have done so
... thanks Adam... learned again.
On Wed, May 18, 2022 at 10:28 AM Ádám Sághy wrote:
> Hi guys,
>
> So lets see what i know about this functionality:
>
> - The Fineract is the publisher and also a listener for the Notification
> events.
>
> - Fineract is publishing notifications in the following
Hi guys,
So lets see what i know about this functionality:
- The Fineract is the publisher and also a listener for the Notification events.
- Fineract is publishing notifications in the following situations:
"ACTIVATE_CLIENT"
"ACTIVATE_CENTER"
"ACTIVATE_GROUP"
"READ_SAVINGSACCOUNT"
"READ_DIVIDEN
... other question: does it do anything? I'll have another look at it
today, but it seems non-functional.
It's going to be hard to reach in general a consensus if people are not
participating... same argument could be made for introducing Liquibase; I'm
sure that others invested time in Flyway, bu
Hello Aleks and Arnold,
I won't remove that feature given we don't know who may or may not be using
it.
There are people using Fineract who are not even on this dev list or
participating in conversations.
I would be careful with what I remove even if it looks unusable to me.
On Wed, May 18, 202
Hi Wilfred,
I'm glad you tried it out locally and even happier that the upgrade worked.
Generally speaking the upgrade path should be as you said it. First to 1.6
and then 1.7. Now, I'd say it's much better if you deploy Fineract 1.6 onto
your server to upgrade the 1.5 database and then do an imm
11 matches
Mail list logo
