[
https://issues.apache.org/jira/browse/FINERACT-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18100196#comment-18100196
]
Adam Saghy commented on FINERACT-2475:
--------------------------------------
[~lea33] Lets create new changeset and by default they should not be enabled.
> Implement Business Events for missing Client lifecycle transitions
> ------------------------------------------------------------------
>
> Key: FINERACT-2475
> URL: https://issues.apache.org/jira/browse/FINERACT-2475
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Nidhi Bhawari
> Priority: Major
> Labels: beginner, beginner-friendly
>
> Currently, the Business Event Framework within the Client module is
> incomplete. It supports events for Creation, Activation, and Rejection, but
> critical lifecycle transitions such as Closing, Withdrawing, Reactivating,
> and the "Undo" actions (Undo Rejection/Withdrawal) do not emit business
> events.
> *Goal:* Achieve full lifecycle event coverage for the Client entity. This
> aligns with the project's goal (FINERACT-2022) to move toward a robust
> Event-Driven Architecture (EDA), allowing external systems to react to all
> client state changes in real-time.
> *Proposed Changes:*
> # Implement 5 new event classes extending {{{}ClientBusinessEvent{}}}:
> ** {{ClientCloseBusinessEvent}}
> ** {{ClientWithdrawBusinessEvent}}
> ** {{ClientReactivateBusinessEvent}}
> ** {{ClientUndoRejectionBusinessEvent}}
> ** {{ClientUndoWithdrawalBusinessEvent}}
> # Update {{ClientWritePlatformServiceJpaRepositoryImpl}} to notify the
> {{BusinessEventNotifierService}} after successful database persistence for
> these transitions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
