Uploaded image for project: 'Apache Fineract'
  1. Apache Fineract
  2. FINERACT-405

Client/Staff SMS phone number back-end validation, incl. default country code

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments


    • Type: New Feature
    • Status: Open
    • Priority: Trivial
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 1.5.0
    • Component/s: None
    • Labels:


      Reported by Michael Vorburger at https://mifosforge.jira.com/browse/MIFOSX-779

      Original Description:
      We'll likely start with just using String / VARCHAR as type for SMS phone numbers in client/staff, but in order get serious about SMS support, the "data quality" of those will quickly be fairly import.
      Therefore, it would probably be very useful if the platform technically enforced that such phone numbers are always represented and stored in the database including country code prefix (using the +91 ... notation).
      The should also have some validation logic in the UI enforcing this (FrontlineSMS says: "This number is not in international format. This may cause problems matching messages to contacts.").
      The UI could assist in making it easier to capture phone numbers and propose a default country code saved in some System Administration configuration somewhere when entering new phone numbers.
      The Java back-end could use some proper strongly typed self validating PhoneNumber value object type, instead of just passing around String? May be something like this exists already?


        Issue Links



            • Assignee:
              santoshmath Santosh Math


              • Created:

                Issue deployment