Hi Nesrine, You have brought up some excellent questions below. I will try to answer them and hopefully if there is any additional or incorrect information, Emily can also chime in.
> Currently we are able to define additional fields using Mifos interface. > However I have noticed that the user is unable to remove an additional > field after its creation. What is the logic behind this knowing that we > are unable to remove those fields despite the fact that they are not > already used in the system?" In general, Mifos has not yet been designed for 'deletion' of any entities in the system (products, offices, holidays, etc). This is pretty consistent with that design and I think it's a future enhancement to look at which entities can be deleted from the system under which circumstances. For example, do you allow users to delete additional fields only when they are not already in use in the system or can you allow them to be deleted also when in use but handle it as a 'logical delete' rather than 'physical delete' in the system so it can continue to be used by reporting, etc. In the meantime, before we analyse and add that functionality to delete things in Mifos, you can probably just mark the 'additional field' as hidden so that it doesn't show up in the data-entry screens anymore, essentially making it non-existent. > Moreover, for look up options definition I noticed that we have the same > problem: we can't remove the look up values from the list boxes. Besides > the look up values defined through the configuration module are not taken > into account in the appropriate list boxes (not displayed in the list > boxes in the appropriate pipeline). The first area, where you cannot delete values from the list, is by design. Again, this could be a future area for enhancement, but is not handled in the design now. The fact that the values you are entering are not showing up in the appropriate list boxes is definitely an error. You should enter that into the issue tracker so we can have that looked into and fixed. When you enter the issue, let us know the specific lookup values that are not working and what values you are trying to enter that are not showing up (e.g. do they contain special characters or characters with accents on them like é, è, à...etc). > When trying to enter labels in French language, there are some letters > that are not displayed correctly, such as: é, è, à...etc. How to handle this > > this? Again, this is definitely a bug. We should be able to handle those types of characters on label fields. Can you enter an item in the issue tracker so we can look into this and fix it? Thanks so much for raising these issues Nesrine. Please let me know if you have any additional questions. Thanks, Aliya ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mifos-functional mailing list Mifos-functional@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mifos-functional
