You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Awasum Yannick (Jira)" <ji...@apache.org> on 2019/11/12 22:35:00 UTC

[jira] [Commented] (FINERACT-527) Enhancing Notification Framework

    [ https://issues.apache.org/jira/browse/FINERACT-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16972852#comment-16972852 ] 

Awasum Yannick commented on FINERACT-527:
-----------------------------------------

[~courage], Why is this still open? Has it not been merged? If your work had been merged then lets close this. Else tell us what is pending so we can record the requirements.

> Enhancing Notification Framework
> --------------------------------
>
>                 Key: FINERACT-527
>                 URL: https://issues.apache.org/jira/browse/FINERACT-527
>             Project: Apache Fineract
>          Issue Type: Improvement
>          Components: Organization, User Management
>    Affects Versions: 1.1.0
>            Reporter: Courage Angeh
>            Priority: Major
>
> *Workdone*
> * Access if activeMQ is active, if so enable activeMQ else use Spring's built in tool called Spring Event
> * User subscription to topic when user account is created
> * Create topics for an organization based on roles in that organization, when the organization is created
> *  Upgrade process of user notification
> *  Migration script - topic, topic subscription models for new and already existing users and organizations
> * Update user subscription on user transfer and/or update of user's permission
> *  Update topic details when entity details updates
> *  Update topic details when member type are updated at the system level
> *  Unit test topic-subscriber model



--
This message was sent by Atlassian Jira
(v8.3.4#803005)