Binny,
As I think through all the projects we have proposed for GSoC around
workflows, notifications, CRM, and business rules, I recognize more deeply
how they're all tied together and how important they factor into the client
management pillar of our financial inclusion roadmap.
At least in my eyes (non-technical and non-functional expert) I'm having
trouble visualizing them from a design and architecture perspective. Both
in how far along we are currently and how inter-connected they are.
Could we spend some time to document how far we are currently and at a
high-level the platform API-layer and database layer work that interns
would need to carry out.
This exercise is also to ensure we haven't left anything out fundamentally
in the platform that would block the interns from doing productive work
that we can merge back in.
Some specific questions I have (and I realize that often you won't be the
best person to respond to these since you're relatively fresh to the Mifos
X codebase):
Workflows
-
Do we have the baseline workflows in place across all the
records/entities in Mifos X (similar to Mifos)
-
I might be muddling client and loan state workflows?
-
Do we have these diagramed out anywhere yet? - (if not, that's a good
task for our documentation volunteers)
-
With these baseline workflows in place,this then the foundation in which
we are able to attach actions or items triggered by these workflows?
-
I.e. attach survey to view or create client stage
-
Trigger an activity when a loan goes into arrears or bad standing
Notifications and system-wide alerts (activity-driven MIS)
-
Is the workflows engine a pre-requisite for following scenarios?
-
Client goes into approval state >> Branch manager gets notification that
a client needs to be approved
-
Loan goes into 60 days in arrears >> field officer or manager gets
notification to follow up with client.
Business Rules Engine
Is this a logical progression of where we're heading?
-
Once we have a workflows engine in place, could hard code that when a
loan goes into 60 days in arrears, a notification should go out to
management, or it could trigger a task/activity for a loan officer.
-
If we had a business rules engine, this condition + action would be a
setting that could be configured from the Mifos X UI
-
i.e. Ops Manager could set # of days in arrears, what
action/notification/etc would get triggered
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Mifos-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-users
