|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________ Mifos-issues mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-issues
Vishwas,
Re-opening issue to make the following comment:
Is it fair to assume that given that this feature is about allowing support for unique identifiers of clients and protecting against client duplication that there should be contraints in place on backend that only allow for 'one identity type per customer' and as each value is a 'unique identity number' that I should get an error back when adding same number for any client.
Please feel free to close this if you think its not relevant or want to postpone putting in contraints around this until later (might make seperate JIRA for it so)