|
Once the basic MIFOSX-754 / MIFOSX-770 / MIFOSX-771 / MIFOSX-774 + MIFOSX-777 kind of infrastructure is available (or, at least analysis, in parallel), we could build the "SMS campaigns" feature some of us discussed at the Mifos Summit in Jaipur in October 2013.
The idea here would be something like this, this likely needs further thought and review by others:
Administrator uses new menu to configure Campaigns. UI lists available Campaigns, with usual New / Delete. The New / Edit campaign UI is:
Name: [ ] Query: [drop-down with ALL available stretchyreports???] Template: [drop-down with all templates of type "campaign"] Type: SMS / Email
Ideally, one could create a new linked "stretchyreport" query and template in this screen, or easily jump to the respective screen and get the ID back, but that's nice to have.
campaign DB table: id | name | inputStretchyReportQueryId | inputStretchyReportParameters (maybe sub-table) | outputTemplateId
We should not force Client or Staff to have to have a mobile number in the database (as some won't, and end-users will invariably just hack around required fields by putting in dummy numbers, which will only lead to other problems). The respective Campaign query used for bulk should filter out Client or Staff. If this is not the case and certain returned rows do not contain a phone number, the campaign query result processor will simply log an error and disregard the respective row. Administrators could easily define additional separate "campaigns" which emails or SMSs lists of clients or staff which do not have a mobile number or email address listed to their respective branch or LO etc.
Invalid phone numbers cannot be detected by the campaign query result processor. Messages are simply sent to numbers as-is, and the respective SMS Gateway implementation will set the status on the respective message to Declined.
|