Title: Message Title
|
|
|
|
|
|
Based on the REST API to be made available under MIFOSX-770, the goal of this task is to build the very first UI in the new AngularJS-based openMF/community-app actually using the new /sms REST API from the Mifos X back-end platform.
As outlined e.g. on MIFOSX-119 and on several pages on the Mifos Wiki, we'd like to start by having a "Send SMS" action on the staff details page, you type something into a text box, it uses the REST API to send it.
Furthermore, the staff details page view should also have some kind of new tab or section listing all SMS previously sent to that staff (manually via the UI from above, or automatically by some future features), or currently being queued to be sent, by a simple table presenting the results of the GET /sms REST API.
Manual sending UI has to not make it possible to use if client/staff (receiver) does not have mobile phone number in the system. Ideally a tooltip "Cannot send SMS as no phone number.".
If the current user does not have the Mifos X Permission to Send SMS or Send Email, then the respective UI elements must not be shown.
Sending SMS to MFI staff is a higher priority than sending to client (for which issue TBD is basically requesting the same).
You could start working on this based on MIFOSX-770, which should just log a test SMS to stdout, even if MIFOSX-771 being worked on in parallel is not yet available.
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues